Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661481f5c0dc6876fc453f23c1a0cd9c40d73084b95e619627d24eb68665ecf9

Tx prefix hash: 4e445cd8258df743afaa3f22383033cf60050dbcc58338d41c755b1ea8eb663a
Tx public key: 05e656395c129741e0e1280ea7676f540e4c04090cf97191fb5ec70313aa7c8c
Timestamp: 1719593174 Timestamp [UCT]: 2024-06-28 16:46:14 Age [y:d:h:m:s]: 00:329:12:28:32
Block: 1054174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235508 RingCT/type: yes/0
Extra: 0105e656395c129741e0e1280ea7676f540e4c04090cf97191fb5ec70313aa7c8c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3861f312cc66403e6d69c7174748549a1a0676f26659960a7234f1325a5dc65 0.600000000000 1524533 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": 1054184, "vin": [ { "gen": { "height": 1054174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3861f312cc66403e6d69c7174748549a1a0676f26659960a7234f1325a5dc65" } } ], "extra": [ 1, 5, 230, 86, 57, 92, 18, 151, 65, 224, 225, 40, 14, 167, 103, 111, 84, 14, 76, 4, 9, 12, 249, 113, 145, 251, 94, 199, 3, 19, 170, 124, 140, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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