Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f2a5e40e23e7547ac6b30fac19da3e185d7288c7779a5a7ea600e0b1957ed77

Tx prefix hash: f2c6abf3ca571f77239b4bb034ca1cedc089b5fb1b926b18819e561dd88a276d
Tx public key: 3ed0bb7ea64254e3f98164e551ff55a62e88230c5333e5e1fd352f11950cd27d
Timestamp: 1720538586 Timestamp [UCT]: 2024-07-09 15:23:06 Age [y:d:h:m:s]: 00:270:20:55:50
Block: 1062027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193516 RingCT/type: yes/0
Extra: 013ed0bb7ea64254e3f98164e551ff55a62e88230c5333e5e1fd352f11950cd27d021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0908442c7e64d8c69f3702843ac33b8ce9b762b7dabec6e5f982baf59ed8f243 0.600000000000 1532528 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": 1062037, "vin": [ { "gen": { "height": 1062027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0908442c7e64d8c69f3702843ac33b8ce9b762b7dabec6e5f982baf59ed8f243" } } ], "extra": [ 1, 62, 208, 187, 126, 166, 66, 84, 227, 249, 129, 100, 229, 81, 255, 85, 166, 46, 136, 35, 12, 83, 51, 229, 225, 253, 53, 47, 17, 149, 12, 210, 125, 2, 17, 0, 0, 0, 17, 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