Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea3d31b7dd793163f32186f613f45aa8d7b6887c002bc326bab3f802fdbef1a

Tx prefix hash: b6a15679d86e794f1c44853e102f748b1c1d2f37f34c6a444b5903b3d4fcfad0
Tx public key: 6998ef7a21f444a43b5e179bebda1277a724d48c9c4ddf09f82cef3445adde16
Timestamp: 1721563204 Timestamp [UCT]: 2024-07-21 12:00:04 Age [y:d:h:m:s]: 00:172:15:56:55
Block: 1070507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123546 RingCT/type: yes/0
Extra: 016998ef7a21f444a43b5e179bebda1277a724d48c9c4ddf09f82cef3445adde16021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9f5e5c6985a9087a5137883a106ca9ab8256e6c0be2c66dc1545214d2e3cd6 0.600000000000 1542368 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": 1070517, "vin": [ { "gen": { "height": 1070507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9f5e5c6985a9087a5137883a106ca9ab8256e6c0be2c66dc1545214d2e3cd6" } } ], "extra": [ 1, 105, 152, 239, 122, 33, 244, 68, 164, 59, 94, 23, 155, 235, 218, 18, 119, 167, 36, 212, 140, 156, 77, 223, 9, 248, 44, 239, 52, 69, 173, 222, 22, 2, 17, 0, 0, 0, 3, 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