Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ba255886b8fac46e64c50f1167d96a6cc9c024d0c4f57778e3c5ef6bcb602b6

Tx prefix hash: 07f885ae2ad561ab9ed1ab3c5f62b7f0ebcfc89db71d51ec2c33455be50ca4a5
Tx public key: 0bdf20a66f61a62966c9cd60be76bec0d9584db010c70c2413c7e4ec3d8520f7
Timestamp: 1675461098 Timestamp [UCT]: 2023-02-03 21:51:38 Age [y:d:h:m:s]: 02:025:15:46:23
Block: 689185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539925 RingCT/type: yes/0
Extra: 010bdf20a66f61a62966c9cd60be76bec0d9584db010c70c2413c7e4ec3d8520f70211000000105029cbac000000000000000000

1 output(s) for total of 3.194801869000 dcy

stealth address amount amount idx
00: 13036798d8c6e4cafc1f82094adce2806d1e9977fbcca8341c955c567f2bde74 3.194801869000 1131849 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": 689195, "vin": [ { "gen": { "height": 689185 } } ], "vout": [ { "amount": 3194801869, "target": { "key": "13036798d8c6e4cafc1f82094adce2806d1e9977fbcca8341c955c567f2bde74" } } ], "extra": [ 1, 11, 223, 32, 166, 111, 97, 166, 41, 102, 201, 205, 96, 190, 118, 190, 192, 217, 88, 77, 176, 16, 199, 12, 36, 19, 199, 228, 236, 61, 133, 32, 247, 2, 17, 0, 0, 0, 16, 80, 41, 203, 172, 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