Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 404c9cdd5c712623572546f72d1194b7a0e7501f700ce791262c59f5924ea097

Tx prefix hash: 9134d83a2fbdae382b911d427caf51c55d71573b350898ed0de5dc9a228c24b5
Tx public key: 3f1fd7b3c067eaa69d9fac380bcc2b94d91d32fd46dd29be503b2a809bf291ad
Timestamp: 1684740063 Timestamp [UCT]: 2023-05-22 07:21:03 Age [y:d:h:m:s]: 01:284:07:09:53
Block: 765488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464370 RingCT/type: yes/0
Extra: 013f1fd7b3c067eaa69d9fac380bcc2b94d91d32fd46dd29be503b2a809bf291ad02110000000633af99f4000000000000000000

1 output(s) for total of 1.784927856000 dcy

stealth address amount amount idx
00: d7e7a91d1c45c8ecdd0aff3794b832fd7a25ffdc13112ffd957e968ae6c803e2 1.784927856000 1214475 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 765498, "vin": [ { "gen": { "height": 765488 } } ], "vout": [ { "amount": 1784927856, "target": { "key": "d7e7a91d1c45c8ecdd0aff3794b832fd7a25ffdc13112ffd957e968ae6c803e2" } } ], "extra": [ 1, 63, 31, 215, 179, 192, 103, 234, 166, 157, 159, 172, 56, 11, 204, 43, 148, 217, 29, 50, 253, 70, 221, 41, 190, 80, 59, 42, 128, 155, 242, 145, 173, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8