Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed99735fad724e3af87ec2227effba587e58f3e639fe966482a5a5a645e85f5c

Tx prefix hash: 2a43805e2a6fdba29c0c6dfacc63c6319145bb60eb381ab967ad4d9e05f1777b
Tx public key: 11a9e0e5c3e9e629e01a08761cfa9258e16e7ef0a09ab1a3314735d9518d4c06
Timestamp: 1697413096 Timestamp [UCT]: 2023-10-15 23:38:16 Age [y:d:h:m:s]: 01:241:09:47:45
Block: 870498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433554 RingCT/type: yes/0
Extra: 0111a9e0e5c3e9e629e01a08761cfa9258e16e7ef0a09ab1a3314735d9518d4c0602110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.801085354000 dcy

stealth address amount amount idx
00: 2a0f696971d2c07f7d0349315dc4144bc80cb72bca4078c3114be058524d0e8d 0.801085354000 1325377 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": 870508, "vin": [ { "gen": { "height": 870498 } } ], "vout": [ { "amount": 801085354, "target": { "key": "2a0f696971d2c07f7d0349315dc4144bc80cb72bca4078c3114be058524d0e8d" } } ], "extra": [ 1, 17, 169, 224, 229, 195, 233, 230, 41, 224, 26, 8, 118, 28, 250, 146, 88, 225, 110, 126, 240, 160, 154, 177, 163, 49, 71, 53, 217, 81, 141, 76, 6, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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