Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41770996845e921143f9a63f1e4db6c5b9726d27c341288c786d75fa59b34c21

Tx prefix hash: e0f6f2678bfae74574c82b5f745111653748c76d8d99b6247fb22e56d79c6d0a
Tx public key: abbd95100d2d96b32ac0669e3595618d236166ce839b75a8f94581b311154105
Timestamp: 1727518255 Timestamp [UCT]: 2024-09-28 10:10:55 Age [y:d:h:m:s]: 00:176:03:22:27
Block: 1119888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125698 RingCT/type: yes/0
Extra: 01abbd95100d2d96b32ac0669e3595618d236166ce839b75a8f94581b311154105021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4578a1aeba2dd7b3c6c5b3aea2c40465e3addd2348cf5f46e4b977e862f8c50e 0.600000000000 1601611 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": 1119898, "vin": [ { "gen": { "height": 1119888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4578a1aeba2dd7b3c6c5b3aea2c40465e3addd2348cf5f46e4b977e862f8c50e" } } ], "extra": [ 1, 171, 189, 149, 16, 13, 45, 150, 179, 42, 192, 102, 158, 53, 149, 97, 141, 35, 97, 102, 206, 131, 155, 117, 168, 249, 69, 129, 179, 17, 21, 65, 5, 2, 17, 0, 0, 0, 7, 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