Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 741f735db99e2ec5d337aa586c8410359e3a6dc9d39edd10ccc7a2bc8583d5d3

Tx prefix hash: 5c433233bcc7a8e65b5fa2d2fa7b4afa636caf0c4fe8e435acdcf7036eaae6ff
Tx public key: 8039309bf04ae70810b1b1f860e38609695a4493394d7899e9507833f064ba2f
Timestamp: 1719598456 Timestamp [UCT]: 2024-06-28 18:14:16 Age [y:d:h:m:s]: 00:280:20:23:57
Block: 1054215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200688 RingCT/type: yes/0
Extra: 018039309bf04ae70810b1b1f860e38609695a4493394d7899e9507833f064ba2f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e46a3ad7d7ab364a1603902c78c698f7b50a04315d7f38c9a5e7562c80409ed 0.600000000000 1524576 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": 1054225, "vin": [ { "gen": { "height": 1054215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e46a3ad7d7ab364a1603902c78c698f7b50a04315d7f38c9a5e7562c80409ed" } } ], "extra": [ 1, 128, 57, 48, 155, 240, 74, 231, 8, 16, 177, 177, 248, 96, 227, 134, 9, 105, 90, 68, 147, 57, 77, 120, 153, 233, 80, 120, 51, 240, 100, 186, 47, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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