Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9457097cfef591b2f5bec1ed2ff5f6fec52f6b3ef80e821fc36e51154263ad22

Tx prefix hash: ea86897ed6ec61c71c7b5652c9370556d6f93c929aca7900a4a08d92a3996104
Tx public key: 8945c259dc3fb67971223bf8e15c7ed2c513502eb0e33957ec7aa62ca40d845d
Timestamp: 1716350966 Timestamp [UCT]: 2024-05-22 04:09:26 Age [y:d:h:m:s]: 00:324:15:15:53
Block: 1027310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232033 RingCT/type: yes/0
Extra: 018945c259dc3fb67971223bf8e15c7ed2c513502eb0e33957ec7aa62ca40d845d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b341145ae08a1b4f484d72161c3f9060b0b1953650f5f5d0ed36653b04dd2d 0.600000000000 1494857 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": 1027320, "vin": [ { "gen": { "height": 1027310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b341145ae08a1b4f484d72161c3f9060b0b1953650f5f5d0ed36653b04dd2d" } } ], "extra": [ 1, 137, 69, 194, 89, 220, 63, 182, 121, 113, 34, 59, 248, 225, 92, 126, 210, 197, 19, 80, 46, 176, 227, 57, 87, 236, 122, 166, 44, 164, 13, 132, 93, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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