Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07eba5156c97691f6c37df7b344e7c2b9273efd0ff062ec55b3391129dddc474

Tx prefix hash: 258505cd78c1280122061352969714b3428b530edb29aefe3ad83ab098f1c2e5
Tx public key: fd9d56f1400505f3193c8e63982cc8f23c1bfb17061423e35b0a560740a8c8dc
Timestamp: 1723291395 Timestamp [UCT]: 2024-08-10 12:03:15 Age [y:d:h:m:s]: 00:235:03:14:34
Block: 1084849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167928 RingCT/type: yes/0
Extra: 01fd9d56f1400505f3193c8e63982cc8f23c1bfb17061423e35b0a560740a8c8dc02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f3642d02add7f6f1e36c93448a292ff62510511e29180e8336ce6eb6c161cb4 0.600000000000 1559272 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": 1084859, "vin": [ { "gen": { "height": 1084849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f3642d02add7f6f1e36c93448a292ff62510511e29180e8336ce6eb6c161cb4" } } ], "extra": [ 1, 253, 157, 86, 241, 64, 5, 5, 243, 25, 60, 142, 99, 152, 44, 200, 242, 60, 27, 251, 23, 6, 20, 35, 227, 91, 10, 86, 7, 64, 168, 200, 220, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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