Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11a9b1fb3d9fa30c01f87bcf0b4e64210d40dfaf7a99d8ade1372370824c4783

Tx prefix hash: 27c31d4d15f6c6df7d250f9e1d5ac8688838cb7b03c33b4a85ce3ad60b0e3584
Tx public key: 83c95af1835cb48be30ba4ef7ea2c6bce65536f8e164f8d97dd61be596d40e2e
Timestamp: 1718453017 Timestamp [UCT]: 2024-06-15 12:03:37 Age [y:d:h:m:s]: 00:319:08:02:15
Block: 1044744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228199 RingCT/type: yes/0
Extra: 0183c95af1835cb48be30ba4ef7ea2c6bce65536f8e164f8d97dd61be596d40e2e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e8c99813868e286b5d658f37896e7de98c1e08be8773d7d4f29d6b0053439e8 0.600000000000 1514133 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": 1044754, "vin": [ { "gen": { "height": 1044744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e8c99813868e286b5d658f37896e7de98c1e08be8773d7d4f29d6b0053439e8" } } ], "extra": [ 1, 131, 201, 90, 241, 131, 92, 180, 139, 227, 11, 164, 239, 126, 162, 198, 188, 230, 85, 54, 248, 225, 100, 248, 217, 125, 214, 27, 229, 150, 212, 14, 46, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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