Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b65821129a1e47b6f0c9ba2ffcb6365ddf9922cba82778023fbbfc5073c1571

Tx prefix hash: a9ef10b35c0d0d5904f68a168cb3b93eaeac0d44ad9732a027c36532bf9d61c2
Tx public key: ae176a77e95a07ae23c4d5838df863fea137f0c239d740ab8d04d711f9cb2c6a
Timestamp: 1673585519 Timestamp [UCT]: 2023-01-13 04:51:59 Age [y:d:h:m:s]: 02:136:15:23:59
Block: 673628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619368 RingCT/type: yes/0
Extra: 01ae176a77e95a07ae23c4d5838df863fea137f0c239d740ab8d04d711f9cb2c6a0211000000018b7b6602000000000000000000

1 output(s) for total of 3.597416743000 dcy

stealth address amount amount idx
00: 4fea595897d684692c27068b5b94f01240da9c94427c393002bbcdfa07d1d4c6 3.597416743000 1115243 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": 673638, "vin": [ { "gen": { "height": 673628 } } ], "vout": [ { "amount": 3597416743, "target": { "key": "4fea595897d684692c27068b5b94f01240da9c94427c393002bbcdfa07d1d4c6" } } ], "extra": [ 1, 174, 23, 106, 119, 233, 90, 7, 174, 35, 196, 213, 131, 141, 248, 99, 254, 161, 55, 240, 194, 57, 215, 64, 171, 141, 4, 215, 17, 249, 203, 44, 106, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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