Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0504dbc6034e8f4b2dc81595601d1e75ae3023acf84fb8cec2997993b8307152

Tx prefix hash: 6a9470d7412ed16e342e537c5472d2a31a34f9e3f3622e7b3674cde8fa231a43
Tx public key: f4b7da28ecddde9126be9c178c18849a72d7b16a6e5c27a6e39f010745c5f4f5
Timestamp: 1728106908 Timestamp [UCT]: 2024-10-05 05:41:48 Age [y:d:h:m:s]: 00:054:12:38:33
Block: 1124759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38968 RingCT/type: yes/0
Extra: 01f4b7da28ecddde9126be9c178c18849a72d7b16a6e5c27a6e39f010745c5f4f502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d24e860fdceb1521f76376981f959ce7b7e75124a982ae2f0f2ef12ffae9a7b 0.600000000000 1607426 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": 1124769, "vin": [ { "gen": { "height": 1124759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d24e860fdceb1521f76376981f959ce7b7e75124a982ae2f0f2ef12ffae9a7b" } } ], "extra": [ 1, 244, 183, 218, 40, 236, 221, 222, 145, 38, 190, 156, 23, 140, 24, 132, 154, 114, 215, 177, 106, 110, 92, 39, 166, 227, 159, 1, 7, 69, 197, 244, 245, 2, 17, 0, 0, 0, 4, 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