Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786cc7ffc972dfd574e862be0fe369338a9d8d9a18c37b2d5f2e64cc0d2275e7

Tx prefix hash: 22aab9014cc494573cb83f6f9afc8f73dfa8cf78091afdc3b7857725818734ad
Tx public key: 936cfa401aacf17cf663d479f9067a6f95aa69fe3b81b259ebd04adbdb6d0896
Timestamp: 1764204723 Timestamp [UCT]: 2025-11-27 00:52:03 Age [y:d:h:m:s]: 00:056:01:14:01
Block: 1420906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39991 RingCT/type: yes/0
Extra: 01936cfa401aacf17cf663d479f9067a6f95aa69fe3b81b259ebd04adbdb6d089602110000000fd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a96fe2a7231c10168bf730873d29ead210098d25a81af0652ef9da99aeef53c 0.600000000000 1909461 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": 1420916, "vin": [ { "gen": { "height": 1420906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a96fe2a7231c10168bf730873d29ead210098d25a81af0652ef9da99aeef53c" } } ], "extra": [ 1, 147, 108, 250, 64, 26, 172, 241, 124, 246, 99, 212, 121, 249, 6, 122, 111, 149, 170, 105, 254, 59, 129, 178, 89, 235, 208, 74, 219, 219, 109, 8, 150, 2, 17, 0, 0, 0, 15, 214, 225, 157, 124, 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