Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83d68e3554a62077dfa5ba6e2e52a0e31990d4362b753fde0328ea36a1bd538b

Tx prefix hash: 609657e196965d7b2a885a19fe90adce67ef551f12e4c28e10472fef7af80e45
Tx public key: 67e6d4462a4c82685dab869c7495f5224d400eae7a039d6733a5d7627e5e3546
Timestamp: 1735469394 Timestamp [UCT]: 2024-12-29 10:49:54 Age [y:d:h:m:s]: 00:117:02:37:08
Block: 1185670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83503 RingCT/type: yes/0
Extra: 0167e6d4462a4c82685dab869c7495f5224d400eae7a039d6733a5d7627e5e35460211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9113d86e91797fac806cb72dfdc35d78276c8ecd93a95b4257c91d1f7f492813 0.600000000000 1672145 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": 1185680, "vin": [ { "gen": { "height": 1185670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9113d86e91797fac806cb72dfdc35d78276c8ecd93a95b4257c91d1f7f492813" } } ], "extra": [ 1, 103, 230, 212, 70, 42, 76, 130, 104, 93, 171, 134, 156, 116, 149, 245, 34, 77, 64, 14, 174, 122, 3, 157, 103, 51, 165, 215, 98, 126, 94, 53, 70, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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