Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f7c21fd8ed973482cf8f919fcb70348e0888b23e614863d67fd9fa90b9bee7b

Tx prefix hash: 2a1e51e8e0b651bb13926be3bee06e3e52efc80f75b1179b3e3f96284815f2ae
Tx public key: f8bdc2d1c5e597c79ab1cf6d757a607a26fdc56ef589f5c605abcd0931733462
Timestamp: 1721200446 Timestamp [UCT]: 2024-07-17 07:14:06 Age [y:d:h:m:s]: 00:220:20:46:14
Block: 1067526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157718 RingCT/type: yes/0
Extra: 01f8bdc2d1c5e597c79ab1cf6d757a607a26fdc56ef589f5c605abcd0931733462021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aac86532e730e86b10fa61c100d5f70000e13ee7baeb28ac0557244407d5c8c6 0.600000000000 1538355 of 15

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": 1067536, "vin": [ { "gen": { "height": 1067526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac86532e730e86b10fa61c100d5f70000e13ee7baeb28ac0557244407d5c8c6" } } ], "extra": [ 1, 248, 189, 194, 209, 197, 229, 151, 199, 154, 177, 207, 109, 117, 122, 96, 122, 38, 253, 197, 110, 245, 137, 245, 198, 5, 171, 205, 9, 49, 115, 52, 98, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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