Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca4443d2a3c0deb55f7228bb586352f3efa3dd5dc83156e51e3cd166288f733

Tx prefix hash: f731d11737e211dd7d4983870c9d79847aec726d2f7c4e89784365533adb8768
Tx public key: e6242a778aecca55c4c531b73bbb6ca7d40c9c43294229f4d1f6ead7682233ef
Timestamp: 1706836087 Timestamp [UCT]: 2024-02-02 01:08:07 Age [y:d:h:m:s]: 00:349:15:07:05
Block: 948410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250299 RingCT/type: yes/0
Extra: 01e6242a778aecca55c4c531b73bbb6ca7d40c9c43294229f4d1f6ead7682233ef02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb37f6c7edb24b913de38da02d04b3594c615345df0b3394974c8cc944212f66 0.600000000000 1406812 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": 948420, "vin": [ { "gen": { "height": 948410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb37f6c7edb24b913de38da02d04b3594c615345df0b3394974c8cc944212f66" } } ], "extra": [ 1, 230, 36, 42, 119, 138, 236, 202, 85, 196, 197, 49, 183, 59, 187, 108, 167, 212, 12, 156, 67, 41, 66, 41, 244, 209, 246, 234, 215, 104, 34, 51, 239, 2, 17, 0, 0, 0, 8, 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