Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a531240f19c5ce31b2f2fd60ccb322bcc9e47ef4160a9a5fa2783786a01d8e6

Tx prefix hash: 75b95f7e6e27a66fc8fb50d6401b04601bf659624ade172491db1ab2dd571108
Tx public key: 15b88faa0494d1a3e9c4a9121264da77112c6e1a9a6212090c78396a01a9e40f
Timestamp: 1673237885 Timestamp [UCT]: 2023-01-09 04:18:05 Age [y:d:h:m:s]: 02:094:22:03:56
Block: 670728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589522 RingCT/type: yes/0
Extra: 0115b88faa0494d1a3e9c4a9121264da77112c6e1a9a6212090c78396a01a9e40f02110000000152542ceb000000000000000000

1 output(s) for total of 3.677897823000 dcy

stealth address amount amount idx
00: e300637accb1099bdc56f369847cd07a62a1de5a1eb082ed7fd0cb3a70504e52 3.677897823000 1112143 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": 670738, "vin": [ { "gen": { "height": 670728 } } ], "vout": [ { "amount": 3677897823, "target": { "key": "e300637accb1099bdc56f369847cd07a62a1de5a1eb082ed7fd0cb3a70504e52" } } ], "extra": [ 1, 21, 184, 143, 170, 4, 148, 209, 163, 233, 196, 169, 18, 18, 100, 218, 119, 17, 44, 110, 26, 154, 98, 18, 9, 12, 120, 57, 106, 1, 169, 228, 15, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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