Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da9b98deade5bf1dc0b4240ecd49f9b8e4505d19804f9fdc662f2f72a109f98

Tx prefix hash: 892055afa4ad72e801ec46243167a4cb043fbf539046b84058c8fa9bc8328a11
Tx public key: 0de8912629a7fdf8d0e033bfb67e1c34289350425f14437b160aa8e0b151271d
Timestamp: 1726067037 Timestamp [UCT]: 2024-09-11 15:03:57 Age [y:d:h:m:s]: 00:074:03:19:47
Block: 1107853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53007 RingCT/type: yes/0
Extra: 010de8912629a7fdf8d0e033bfb67e1c34289350425f14437b160aa8e0b151271d02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfc7351af29eee958112aa3a1105c44c5c8a39b010ba0d952fadbb853013874b 0.600000000000 1585544 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": 1107863, "vin": [ { "gen": { "height": 1107853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfc7351af29eee958112aa3a1105c44c5c8a39b010ba0d952fadbb853013874b" } } ], "extra": [ 1, 13, 232, 145, 38, 41, 167, 253, 248, 208, 224, 51, 191, 182, 126, 28, 52, 40, 147, 80, 66, 95, 20, 67, 123, 22, 10, 168, 224, 177, 81, 39, 29, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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