Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c940d991b29d2765391e98e20ba3fbcb080feb446a136dafa02d0e3ef2874a92

Tx prefix hash: a5474f74c76857deedd5affb25bdb9f14151bf30e63f679699d4965cb8ca8e4a
Tx public key: 69ee9a970d76e3d6949d55e78463e4eef44b82ed5cf291f4fe8ac9ea6e72d2d6
Timestamp: 1717554878 Timestamp [UCT]: 2024-06-05 02:34:38 Age [y:d:h:m:s]: 00:293:22:01:16
Block: 1037292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210026 RingCT/type: yes/0
Extra: 0169ee9a970d76e3d6949d55e78463e4eef44b82ed5cf291f4fe8ac9ea6e72d2d602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1604c2b72670ea38ae5952403b07f34121ce740d91c2383e560d7aa49fffe84 0.600000000000 1505823 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": 1037302, "vin": [ { "gen": { "height": 1037292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1604c2b72670ea38ae5952403b07f34121ce740d91c2383e560d7aa49fffe84" } } ], "extra": [ 1, 105, 238, 154, 151, 13, 118, 227, 214, 148, 157, 85, 231, 132, 99, 228, 238, 244, 75, 130, 237, 92, 242, 145, 244, 254, 138, 201, 234, 110, 114, 210, 214, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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