Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40c4222aafc1b5a3ba45fc3fe534ef25ec73029f9f58fc4fda900891e9e4175f

Tx prefix hash: 50dcd4cc8a9ba6610c0a887b0c360fba387a2d52135dee6e524bcd60c40e0ba5
Tx public key: 7206cd0b1b8df2a1251e1d9390cba0c90ab94d354ebb904c8b0ff4e56be459e7
Timestamp: 1711707616 Timestamp [UCT]: 2024-03-29 10:20:16 Age [y:d:h:m:s]: 00:287:08:01:26
Block: 988822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205662 RingCT/type: yes/0
Extra: 017206cd0b1b8df2a1251e1d9390cba0c90ab94d354ebb904c8b0ff4e56be459e70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aa4d9f78017c6c025747b8559e52d6a22967db7c8be74a04146515fe3f2f9b7 0.600000000000 1449107 of 15

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": 988832, "vin": [ { "gen": { "height": 988822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aa4d9f78017c6c025747b8559e52d6a22967db7c8be74a04146515fe3f2f9b7" } } ], "extra": [ 1, 114, 6, 205, 11, 27, 141, 242, 161, 37, 30, 29, 147, 144, 203, 160, 201, 10, 185, 77, 53, 78, 187, 144, 76, 139, 15, 244, 229, 107, 228, 89, 231, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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