Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1647ec50974d56f66c1887fa1ec5631d574fe8ad8abbbbfc86fea942731d6d3

Tx prefix hash: 448d61d4d187a8df1c48a5863066b91a0c8f49bcd45ede483e8f5352bf92727e
Tx public key: 357f713d5720b055274e9d23189cfba65f3bd2eee96d3bea55283c9a27aecd46
Timestamp: 1576037393 Timestamp [UCT]: 2019-12-11 04:09:53 Age [y:d:h:m:s]: 05:129:01:59:43
Block: 25129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238105 RingCT/type: yes/0
Extra: 01357f713d5720b055274e9d23189cfba65f3bd2eee96d3bea55283c9a27aecd4602110000000b9159db1e000000000000000000

1 output(s) for total of 506.685015556000 dcy

stealth address amount amount idx
00: d15c236683d21683fb1103a3df8fdc3167f0812bb7ab72ae495ac072ee9d93d8 506.685015556000 41394 of 0

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": 25139, "vin": [ { "gen": { "height": 25129 } } ], "vout": [ { "amount": 506685015556, "target": { "key": "d15c236683d21683fb1103a3df8fdc3167f0812bb7ab72ae495ac072ee9d93d8" } } ], "extra": [ 1, 53, 127, 113, 61, 87, 32, 176, 85, 39, 78, 157, 35, 24, 156, 251, 166, 95, 59, 210, 238, 233, 109, 59, 234, 85, 40, 60, 154, 39, 174, 205, 70, 2, 17, 0, 0, 0, 11, 145, 89, 219, 30, 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