Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74c9b80d79ce0b9593a7d892425fa97b3c4ef7e5dd89ed15b97136e4a5b3581f

Tx prefix hash: 2a3e4cee5895b5ef11a8c30a468e3b34a5886b1a5d4933bddfb0524e248e46b4
Tx public key: 984db4b00c20c585879765ad1a81c80c569871b45550360792c49d311c227729
Timestamp: 1694277605 Timestamp [UCT]: 2023-09-09 16:40:05 Age [y:d:h:m:s]: 01:213:03:06:15
Block: 844489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413423 RingCT/type: yes/0
Extra: 01984db4b00c20c585879765ad1a81c80c569871b45550360792c49d311c22772902110000000633af99f4000000000000000000

1 output(s) for total of 0.976916497000 dcy

stealth address amount amount idx
00: c00fa6055299d6434e04504cb24a389721c3da180a4ffd56c27ebfc39923a3e2 0.976916497000 1297801 of 0

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": 844499, "vin": [ { "gen": { "height": 844489 } } ], "vout": [ { "amount": 976916497, "target": { "key": "c00fa6055299d6434e04504cb24a389721c3da180a4ffd56c27ebfc39923a3e2" } } ], "extra": [ 1, 152, 77, 180, 176, 12, 32, 197, 133, 135, 151, 101, 173, 26, 129, 200, 12, 86, 152, 113, 180, 85, 80, 54, 7, 146, 196, 157, 49, 28, 34, 119, 41, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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