Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c26e9577cee7490cf502c77bad7a40b593a442e2e74dcaf2f6ed27c1e1d1b65

Tx prefix hash: a3741ae6ebf249011d4ed436e1a46f5ae499b9bd483f5c15acbb15b6e816ef58
Tx public key: 31076c5d09be372d468bd4494d3ae5458decf506fdc7130e3dadcc9d42081fc8
Timestamp: 1703052708 Timestamp [UCT]: 2023-12-20 06:11:48 Age [y:d:h:m:s]: 01:148:10:48:51
Block: 917054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367242 RingCT/type: yes/0
Extra: 0131076c5d09be372d468bd4494d3ae5458decf506fdc7130e3dadcc9d42081fc8021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6421e1ed82cefacf08e7e4b323d2c001068ab361cb2b404bab5360fd094501d4 0.600000000000 1374618 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": 917064, "vin": [ { "gen": { "height": 917054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6421e1ed82cefacf08e7e4b323d2c001068ab361cb2b404bab5360fd094501d4" } } ], "extra": [ 1, 49, 7, 108, 93, 9, 190, 55, 45, 70, 139, 212, 73, 77, 58, 229, 69, 141, 236, 245, 6, 253, 199, 19, 14, 61, 173, 204, 157, 66, 8, 31, 200, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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