Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a39b78352dee10681984a3df9bde7a0369f396b72027c07d4a070d5f3ce0a2

Tx prefix hash: 5733aedba4b283dafe29cd0a2ef45fc218de8fe02a7b2af3f8ac13e0459ccbdb
Tx public key: f1ccbd12a2a282eeddabd17b339ccc7f786cd62f7d05a50c2be540d8a6c13518
Timestamp: 1714304010 Timestamp [UCT]: 2024-04-28 11:33:30 Age [y:d:h:m:s]: 00:305:08:28:46
Block: 1010326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218263 RingCT/type: yes/0
Extra: 01f1ccbd12a2a282eeddabd17b339ccc7f786cd62f7d05a50c2be540d8a6c1351802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79b011ab76138ca3827fdc2daae727f2734e33d8813e6dc4918261a188646291 0.600000000000 1472248 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": 1010336, "vin": [ { "gen": { "height": 1010326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79b011ab76138ca3827fdc2daae727f2734e33d8813e6dc4918261a188646291" } } ], "extra": [ 1, 241, 204, 189, 18, 162, 162, 130, 238, 221, 171, 209, 123, 51, 156, 204, 127, 120, 108, 214, 47, 125, 5, 165, 12, 43, 229, 64, 216, 166, 193, 53, 24, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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