Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f60fb5cb59ca323db85b539d387f89dbfa8a7430b2f6e88924c7e3a54e9ec0

Tx prefix hash: 012d80a5ddc2044618e6a34800242f2e53246c9b1023fc96b9c756ffc0d0cc5a
Tx public key: 88ef20cd99d19ae1227dcf8cfd0b609892ca96f264f880d944d155634a85c315
Timestamp: 1694284089 Timestamp [UCT]: 2023-09-09 18:28:09 Age [y:d:h:m:s]: 01:211:13:53:55
Block: 844537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412315 RingCT/type: yes/0
Extra: 0188ef20cd99d19ae1227dcf8cfd0b609892ca96f264f880d944d155634a85c31502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.976558804000 dcy

stealth address amount amount idx
00: 5fcbab8a7d092844357592ae7e6c5d9d139650e70c551300ffc4573222a25b4b 0.976558804000 1297851 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": 844547, "vin": [ { "gen": { "height": 844537 } } ], "vout": [ { "amount": 976558804, "target": { "key": "5fcbab8a7d092844357592ae7e6c5d9d139650e70c551300ffc4573222a25b4b" } } ], "extra": [ 1, 136, 239, 32, 205, 153, 209, 154, 225, 34, 125, 207, 140, 253, 11, 96, 152, 146, 202, 150, 242, 100, 248, 128, 217, 68, 209, 85, 99, 74, 133, 195, 21, 2, 17, 0, 0, 0, 7, 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