Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54275c9773522341c3c64e23c4874678acf2629bfa562ee56d97740fa7f5ee46

Tx prefix hash: 40588d4d5db738c2c8d1ef1ab17979b0f19715686452fde9fd50f7d4276fd0a9
Tx public key: 0865127ca98cdde06622327fe082d0590d366a09f6503b7e9044e2a345c2e45c
Timestamp: 1713902572 Timestamp [UCT]: 2024-04-23 20:02:52 Age [y:d:h:m:s]: 01:190:21:06:50
Block: 1007001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395069 RingCT/type: yes/0
Extra: 010865127ca98cdde06622327fe082d0590d366a09f6503b7e9044e2a345c2e45c02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a956831ac163e1807e66c0f1c882e654aa0f6fefd4c3d47448ae53161ef18df 0.600000000000 1468211 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": 1007011, "vin": [ { "gen": { "height": 1007001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a956831ac163e1807e66c0f1c882e654aa0f6fefd4c3d47448ae53161ef18df" } } ], "extra": [ 1, 8, 101, 18, 124, 169, 140, 221, 224, 102, 34, 50, 127, 224, 130, 208, 89, 13, 54, 106, 9, 246, 80, 59, 126, 144, 68, 226, 163, 69, 194, 228, 92, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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