Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7da31e3e0550b00cd17a1901f3ff82d9a17be3f7e282706e1833e29bb6a56a2

Tx prefix hash: 888b6315b0342d7f13cba8f64d747a4f9277fb3a6f6924e6f4472ebec79b00ec
Tx public key: b2220fe02b9b49ad03be134993df5216d3cdb1b92147a1459f253cc0384c7805
Timestamp: 1728830902 Timestamp [UCT]: 2024-10-13 14:48:22 Age [y:d:h:m:s]: 00:177:02:56:06
Block: 1130772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126362 RingCT/type: yes/0
Extra: 01b2220fe02b9b49ad03be134993df5216d3cdb1b92147a1459f253cc0384c780502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e7424e34229b1517626d5307a8d5da564de4f347b7a57f654fc16ac7f23e441 0.600000000000 1613653 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": 1130782, "vin": [ { "gen": { "height": 1130772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e7424e34229b1517626d5307a8d5da564de4f347b7a57f654fc16ac7f23e441" } } ], "extra": [ 1, 178, 34, 15, 224, 43, 155, 73, 173, 3, 190, 19, 73, 147, 223, 82, 22, 211, 205, 177, 185, 33, 71, 161, 69, 159, 37, 60, 192, 56, 76, 120, 5, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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