Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe0bc9356cf4799ee7155bd184f674377ee97188566e5d92a1da89b3932c37e

Tx prefix hash: 3725f3945140dc4016f7f2569085abceea701e97276cc6ca2db39c1637a1f096
Tx public key: efcf11107773cd6ed5c943cbae758ad8cdccdbf4aff48b3e802bd69f3bf4c58b
Timestamp: 1617125066 Timestamp [UCT]: 2021-03-30 17:24:26 Age [y:d:h:m:s]: 03:339:04:01:22
Block: 229844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1001657 RingCT/type: yes/0
Extra: 01efcf11107773cd6ed5c943cbae758ad8cdccdbf4aff48b3e802bd69f3bf4c58b02110000004c218d0d3b000000000000000000

1 output(s) for total of 106.277056176000 dcy

stealth address amount amount idx
00: 011855924b0f65dbd7cad5a683e4c57d74ef5c4105b95dd799357d92c62c8ee4 106.277056176000 476976 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": 229854, "vin": [ { "gen": { "height": 229844 } } ], "vout": [ { "amount": 106277056176, "target": { "key": "011855924b0f65dbd7cad5a683e4c57d74ef5c4105b95dd799357d92c62c8ee4" } } ], "extra": [ 1, 239, 207, 17, 16, 119, 115, 205, 110, 213, 201, 67, 203, 174, 117, 138, 216, 205, 204, 219, 244, 175, 244, 139, 62, 128, 43, 214, 159, 59, 244, 197, 139, 2, 17, 0, 0, 0, 76, 33, 141, 13, 59, 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