Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381c3bf5d0e3b8ca942e4e460529525f3370a75162f110f508685c16826a9a5e

Tx prefix hash: 057cbf7bc11281f8b4e3f6da5d1c0fafd746f031f18705cde271a9d7e5caa9a5
Tx public key: 91ce5ed6a8a78868ed95e1f795c2106833194544c1beeddda04c3512ee274d79
Timestamp: 1711487259 Timestamp [UCT]: 2024-03-26 21:07:39 Age [y:d:h:m:s]: 00:289:18:57:37
Block: 987010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207401 RingCT/type: yes/0
Extra: 0191ce5ed6a8a78868ed95e1f795c2106833194544c1beeddda04c3512ee274d7902110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 236f397ef183500942d86f8396ed2b4ebe2f55d5d0a25041942bd0e83b10dbc0 0.600000000000 1447249 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": 987020, "vin": [ { "gen": { "height": 987010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "236f397ef183500942d86f8396ed2b4ebe2f55d5d0a25041942bd0e83b10dbc0" } } ], "extra": [ 1, 145, 206, 94, 214, 168, 167, 136, 104, 237, 149, 225, 247, 149, 194, 16, 104, 51, 25, 69, 68, 193, 190, 237, 221, 160, 76, 53, 18, 238, 39, 77, 121, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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