Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47428ba0ba1e2434500acc76f381412887e2f3afb1a9d3e80530d33024431416

Tx prefix hash: 328094451e6314918e73fbe36f3117695fbcf95b42cdfb380d304d3dddb8699e
Tx public key: 806d9277e043076fd3179e9206e4f9a897d2454d7a1e224055eca8424c51d93f
Timestamp: 1728879243 Timestamp [UCT]: 2024-10-14 04:14:03 Age [y:d:h:m:s]: 00:163:10:47:34
Block: 1131174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116567 RingCT/type: yes/0
Extra: 01806d9277e043076fd3179e9206e4f9a897d2454d7a1e224055eca8424c51d93f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb7efb1ea3a3fcd84b1d0fd6c0845dca57d78ac6eecef58c7a2d30fb4cb46833 0.600000000000 1614055 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": 1131184, "vin": [ { "gen": { "height": 1131174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb7efb1ea3a3fcd84b1d0fd6c0845dca57d78ac6eecef58c7a2d30fb4cb46833" } } ], "extra": [ 1, 128, 109, 146, 119, 224, 67, 7, 111, 211, 23, 158, 146, 6, 228, 249, 168, 151, 210, 69, 77, 122, 30, 34, 64, 85, 236, 168, 66, 76, 81, 217, 63, 2, 17, 0, 0, 0, 3, 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