Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7fdd40046769129120a8fc48658a6d82eae69e6133c22de4bcb25db1e119a2e

Tx prefix hash: cd7ba04dbc0b4a50da0ed5a808e821f6400da2418b193f3ca59e41466de81980
Tx public key: 66cdaf97a31d5facdfa51e3a1b0da2d9d1eba94d37001c593c1aa80f6443d5d7
Timestamp: 1645309265 Timestamp [UCT]: 2022-02-19 22:21:05 Age [y:d:h:m:s]: 02:308:01:39:53
Block: 442195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 739592 RingCT/type: yes/0
Extra: 0166cdaf97a31d5facdfa51e3a1b0da2d9d1eba94d37001c593c1aa80f6443d5d7021100000007a8c141c5000000000000000000

1 output(s) for total of 21.029293933000 dcy

stealth address amount amount idx
00: 5df44db56e3ef6081f5b5e22d1642b17e49e35c98ed1bacf512f77568b01e382 21.029293933000 854926 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": 442205, "vin": [ { "gen": { "height": 442195 } } ], "vout": [ { "amount": 21029293933, "target": { "key": "5df44db56e3ef6081f5b5e22d1642b17e49e35c98ed1bacf512f77568b01e382" } } ], "extra": [ 1, 102, 205, 175, 151, 163, 29, 95, 172, 223, 165, 30, 58, 27, 13, 162, 217, 209, 235, 169, 77, 55, 0, 28, 89, 60, 26, 168, 15, 100, 67, 213, 215, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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