Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1a0003fa193f726777c2c55c7b90b392251a17a247a87124c0f54ca43539e9

Tx prefix hash: 75f76feac2d956d5525915e367a35af8847d4379a934c5111f4a74fb56c75edb
Tx public key: eebc4dabc5c98c6d190f504a7f6c1dfc852204139123595ed9e59ea406bbf613
Timestamp: 1720410007 Timestamp [UCT]: 2024-07-08 03:40:07 Age [y:d:h:m:s]: 00:254:06:34:45
Block: 1060953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181684 RingCT/type: yes/0
Extra: 01eebc4dabc5c98c6d190f504a7f6c1dfc852204139123595ed9e59ea406bbf613021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6adb5bdfd53361549aac340c6e2c63ae444d84313c6c3ce4e94f1bae9b8bd73 0.600000000000 1531442 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": 1060963, "vin": [ { "gen": { "height": 1060953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6adb5bdfd53361549aac340c6e2c63ae444d84313c6c3ce4e94f1bae9b8bd73" } } ], "extra": [ 1, 238, 188, 77, 171, 197, 201, 140, 109, 25, 15, 80, 74, 127, 108, 29, 252, 133, 34, 4, 19, 145, 35, 89, 94, 217, 229, 158, 164, 6, 187, 246, 19, 2, 17, 0, 0, 0, 3, 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