Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a37cd81d9d067f39f5fe21eccc0e9053819bbbd320104a8e112be5ea49bf1bdb

Tx prefix hash: 618eb787f6b4bfc539ed8df7ada5e9b2d513ff0711f3a361843a8a51681dc504
Tx public key: 144a79f250f9fd337021a046f5ea66c6c2d40f50c7ff1f8b46bfe9fc09e56b8f
Timestamp: 1729607572 Timestamp [UCT]: 2024-10-22 14:32:52 Age [y:d:h:m:s]: 00:078:17:43:37
Block: 1137167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56299 RingCT/type: yes/0
Extra: 01144a79f250f9fd337021a046f5ea66c6c2d40f50c7ff1f8b46bfe9fc09e56b8f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8722a3f7eaad934bdcdbea1d12fced6bfb2b56af1b3eb8127c287bc36193a2bc 0.600000000000 1620608 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": 1137177, "vin": [ { "gen": { "height": 1137167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8722a3f7eaad934bdcdbea1d12fced6bfb2b56af1b3eb8127c287bc36193a2bc" } } ], "extra": [ 1, 20, 74, 121, 242, 80, 249, 253, 51, 112, 33, 160, 70, 245, 234, 102, 198, 194, 212, 15, 80, 199, 255, 31, 139, 70, 191, 233, 252, 9, 229, 107, 143, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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