Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2611bdcaeb4e936a598df571ddf479153e4cebb1b5bbe59d30fadbfa2bed963

Tx prefix hash: 286c7a8005f1e805a40daeed1b21d5d0a1ef223a0c53f9e83c149849df44be7c
Tx public key: abfe4c074d3e800f747c0238c1dec96dd23c91a09e065491ca3d3d3fc1833c8d
Timestamp: 1722240255 Timestamp [UCT]: 2024-07-29 08:04:15 Age [y:d:h:m:s]: 00:305:19:00:55
Block: 1076129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218497 RingCT/type: yes/0
Extra: 01abfe4c074d3e800f747c0238c1dec96dd23c91a09e065491ca3d3d3fc1833c8d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff6d9d2abadfd71d094a8c2d9313a36306b07842ea898d5ee9adbf7473b05abf 0.600000000000 1548664 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": 1076139, "vin": [ { "gen": { "height": 1076129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff6d9d2abadfd71d094a8c2d9313a36306b07842ea898d5ee9adbf7473b05abf" } } ], "extra": [ 1, 171, 254, 76, 7, 77, 62, 128, 15, 116, 124, 2, 56, 193, 222, 201, 109, 210, 60, 145, 160, 158, 6, 84, 145, 202, 61, 61, 63, 193, 131, 60, 141, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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