Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 718dba48952f07a2ec48eb2b8abdfc310f6de707bff8ab74077941559c14d12a

Tx prefix hash: 867db560bfd153b7782c0d8caded5c7d516012dc368d5d6b26201a14a7ac7e5d
Tx public key: ab0f8c5aef798bbb9f276bd387261ee521ff3b43fe4d513e35d1d712cf2809bf
Timestamp: 1734903618 Timestamp [UCT]: 2024-12-22 21:40:18 Age [y:d:h:m:s]: 00:093:13:38:13
Block: 1181028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66605 RingCT/type: yes/0
Extra: 01ab0f8c5aef798bbb9f276bd387261ee521ff3b43fe4d513e35d1d712cf2809bf02110000000138edce2e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51bf073064090a384f0d0de6ea478902e8e4ac31c44e15c72cabfd4bc8ed7e7f 0.600000000000 1667443 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": 1181038, "vin": [ { "gen": { "height": 1181028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51bf073064090a384f0d0de6ea478902e8e4ac31c44e15c72cabfd4bc8ed7e7f" } } ], "extra": [ 1, 171, 15, 140, 90, 239, 121, 139, 187, 159, 39, 107, 211, 135, 38, 30, 229, 33, 255, 59, 67, 254, 77, 81, 62, 53, 209, 215, 18, 207, 40, 9, 191, 2, 17, 0, 0, 0, 1, 56, 237, 206, 46, 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