Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78dd477aeec9b7f0c33fbacfcef32c52e187d677deacacc3ec3c1d26d3a0020

Tx prefix hash: 01e0fb0bea0fe6f352dd728e43a961f93bd4396fd96299756d278072ee7bef45
Tx public key: f451e8169b28308faed83efb79b9ee4602652a36ce3f025ef0bdb7e4006fef6d
Timestamp: 1709941849 Timestamp [UCT]: 2024-03-08 23:50:49 Age [y:d:h:m:s]: 01:247:14:02:57
Block: 974178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435658 RingCT/type: yes/0
Extra: 01f451e8169b28308faed83efb79b9ee4602652a36ce3f025ef0bdb7e4006fef6d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cf464795b99ab0f49cd1bafbca1dcc8acb8921bee0b1579f88ecb55c368f086 0.600000000000 1434129 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": 974188, "vin": [ { "gen": { "height": 974178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cf464795b99ab0f49cd1bafbca1dcc8acb8921bee0b1579f88ecb55c368f086" } } ], "extra": [ 1, 244, 81, 232, 22, 155, 40, 48, 143, 174, 216, 62, 251, 121, 185, 238, 70, 2, 101, 42, 54, 206, 63, 2, 94, 240, 189, 183, 228, 0, 111, 239, 109, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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