Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d440ecb7a6702cf26ee003754b1de3ca899c8ec656f26e7e05078ea4385bee

Tx prefix hash: 0a7e897107966dc6959d258c0aa7479d629ee2e5380e969aca21b62375da6b48
Tx public key: 948ba862f91533c4a4c4e19ea0c399e5d3c39d2c2e613c4b72fcbf5e328447bf
Timestamp: 1719902668 Timestamp [UCT]: 2024-07-02 06:44:28 Age [y:d:h:m:s]: 00:318:05:43:29
Block: 1056751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227413 RingCT/type: yes/0
Extra: 01948ba862f91533c4a4c4e19ea0c399e5d3c39d2c2e613c4b72fcbf5e328447bf021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a39a0ae0d0cf796072a02a9585b0a5f008dcc206d47c1cb08ab8520b97436a 0.600000000000 1527172 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": 1056761, "vin": [ { "gen": { "height": 1056751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a39a0ae0d0cf796072a02a9585b0a5f008dcc206d47c1cb08ab8520b97436a" } } ], "extra": [ 1, 148, 139, 168, 98, 249, 21, 51, 196, 164, 196, 225, 158, 160, 195, 153, 229, 211, 195, 157, 44, 46, 97, 60, 75, 114, 252, 191, 94, 50, 132, 71, 191, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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