Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111d0819f138223d1c73cbefeaa2b624f2291aa6095a7028d82b3ef06d1661dd

Tx prefix hash: 3172d99793a2b2bf5436da71a6e1c60384f8fae605ee4dd538d5a5df689d5c73
Tx public key: a99ce2388c2f17d3e51c93810be8e48a119dcd20575e4bbf1b7b523591a66418
Timestamp: 1710482595 Timestamp [UCT]: 2024-03-15 06:03:15 Age [y:d:h:m:s]: 01:076:21:03:43
Block: 978665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315961 RingCT/type: yes/0
Extra: 01a99ce2388c2f17d3e51c93810be8e48a119dcd20575e4bbf1b7b523591a664180211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59a9094e5db259579b16ce8e3ea7220b3cf715eef1044ede56ed3a282131016b 0.600000000000 1438694 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": 978675, "vin": [ { "gen": { "height": 978665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59a9094e5db259579b16ce8e3ea7220b3cf715eef1044ede56ed3a282131016b" } } ], "extra": [ 1, 169, 156, 226, 56, 140, 47, 23, 211, 229, 28, 147, 129, 11, 232, 228, 138, 17, 157, 205, 32, 87, 94, 75, 191, 27, 123, 82, 53, 145, 166, 100, 24, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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