Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6201887c16ad04e177798122676fa5f74ca537bb22656e2b09c8b4c286ed96

Tx prefix hash: 60d031e3f3d7330cd5fe4f5b5fbcb868a18a5398b77c2bba2c1171dbee70e74d
Tx public key: 8b2779eac28c4c8d9e7ee0f0b66322a7d2d4e184bc5077fcadb29a291455e53d
Timestamp: 1650897297 Timestamp [UCT]: 2022-04-25 14:34:57 Age [y:d:h:m:s]: 02:190:09:36:47
Block: 487878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655987 RingCT/type: yes/0
Extra: 018b2779eac28c4c8d9e7ee0f0b66322a7d2d4e184bc5077fcadb29a291455e53d021100000009c9067537000000000000000000

1 output(s) for total of 14.841079446000 dcy

stealth address amount amount idx
00: 0b06b64605ea1d9db535bf81f054c3d4ef4d477e8469451a0f539a0c7ab8c295 14.841079446000 910431 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": 487888, "vin": [ { "gen": { "height": 487878 } } ], "vout": [ { "amount": 14841079446, "target": { "key": "0b06b64605ea1d9db535bf81f054c3d4ef4d477e8469451a0f539a0c7ab8c295" } } ], "extra": [ 1, 139, 39, 121, 234, 194, 140, 76, 141, 158, 126, 224, 240, 182, 99, 34, 167, 210, 212, 225, 132, 188, 80, 119, 252, 173, 178, 154, 41, 20, 85, 229, 61, 2, 17, 0, 0, 0, 9, 201, 6, 117, 55, 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