Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d06fec29b72c8d8015c71310f36e8f1ec3ee71a9ccb3afbf90605ee30d1df8

Tx prefix hash: 3a1496c15015f2a15a79751450e308124659927483cc545c87d2d4dfa065e037
Tx public key: 6b8949b34d541e34838d2030a70c22815037fdc2ba3fb2e8f90572c5349ea386
Timestamp: 1724414938 Timestamp [UCT]: 2024-08-23 12:08:58 Age [y:d:h:m:s]: 01:076:00:51:37
Block: 1094178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312768 RingCT/type: yes/0
Extra: 016b8949b34d541e34838d2030a70c22815037fdc2ba3fb2e8f90572c5349ea386021100000005e914dd15000000000000000000

1 output(s) for total of 0.605770000000 dcy

stealth address amount amount idx
00: 435e563601ce0ef22e145148eeb6bf18ff21cd42ba2e1cab39a56cb5408d8aed 0.605770000000 1569267 of 0

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": 1094188, "vin": [ { "gen": { "height": 1094178 } } ], "vout": [ { "amount": 605770000, "target": { "key": "435e563601ce0ef22e145148eeb6bf18ff21cd42ba2e1cab39a56cb5408d8aed" } } ], "extra": [ 1, 107, 137, 73, 179, 77, 84, 30, 52, 131, 141, 32, 48, 167, 12, 34, 129, 80, 55, 253, 194, 186, 63, 178, 232, 249, 5, 114, 197, 52, 158, 163, 134, 2, 17, 0, 0, 0, 5, 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