Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c868cfc352cf4e6a0d47d6574ce3e1e55a7cae1d0cc4b268e43e6a45610f65

Tx prefix hash: ac4b7be074c6f873228b543429745119900463157bd50f988fe6285c824a9782
Tx public key: 17e427d272efe2d79478f5d892a2e88b839fc671b1a78679686f55ff4d952f40
Timestamp: 1730869832 Timestamp [UCT]: 2024-11-06 05:10:32 Age [y:d:h:m:s]: 00:001:03:31:22
Block: 1147582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830 RingCT/type: yes/0
Extra: 0117e427d272efe2d79478f5d892a2e88b839fc671b1a78679686f55ff4d952f40021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42b7d54e9cbb1a50a5ecdeba12f2ab4399ad1442937eed5ad468064fc27bde50 0.600000000000 1632281 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": 1147592, "vin": [ { "gen": { "height": 1147582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b7d54e9cbb1a50a5ecdeba12f2ab4399ad1442937eed5ad468064fc27bde50" } } ], "extra": [ 1, 23, 228, 39, 210, 114, 239, 226, 215, 148, 120, 245, 216, 146, 162, 232, 139, 131, 159, 198, 113, 177, 167, 134, 121, 104, 111, 85, 255, 77, 149, 47, 64, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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