Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b8d0cd121aaa3cc9907967abb81f93f35e33ecef6273ff32906e32f0784ef0

Tx prefix hash: 86b00568d0a3bf7120e1de11e63fd622aab5394642af334a96d66dff6af2a144
Tx public key: 791f098c2212ac775c905aeb6c02d9660cefde20466b4c0a8066b629fc6581b0
Timestamp: 1716516290 Timestamp [UCT]: 2024-05-24 02:04:50 Age [y:d:h:m:s]: 01:168:04:07:05
Block: 1028686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378771 RingCT/type: yes/0
Extra: 01791f098c2212ac775c905aeb6c02d9660cefde20466b4c0a8066b629fc6581b002110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44f4c0d6979551cda361e4d0ee045c91e6f7c33a9f281b6dd45a6428a9de7b1 0.600000000000 1496683 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": 1028696, "vin": [ { "gen": { "height": 1028686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44f4c0d6979551cda361e4d0ee045c91e6f7c33a9f281b6dd45a6428a9de7b1" } } ], "extra": [ 1, 121, 31, 9, 140, 34, 18, 172, 119, 92, 144, 90, 235, 108, 2, 217, 102, 12, 239, 222, 32, 70, 107, 76, 10, 128, 102, 182, 41, 252, 101, 129, 176, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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