Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ec1d5da3106a6a21145a24db5bbf15c53324b05839b138bc3292bb962fe43b

Tx prefix hash: 3b8268bbe66e98a2e7f77f812056d7a065bca1b82b1c142fba3da793aef289c4
Tx public key: 9040923c94d677cfe2048f94a92c2a0a74300b8ea23ebb0f914b4e2b37777726
Timestamp: 1728817389 Timestamp [UCT]: 2024-10-13 11:03:09 Age [y:d:h:m:s]: 01:039:12:58:43
Block: 1130659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286635 RingCT/type: yes/0
Extra: 019040923c94d677cfe2048f94a92c2a0a74300b8ea23ebb0f914b4e2b37777726021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42d32052d3f797923c642be43a1900b3b3ec3f08dbe3351df211a11713b27171 0.600000000000 1613536 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": 1130669, "vin": [ { "gen": { "height": 1130659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42d32052d3f797923c642be43a1900b3b3ec3f08dbe3351df211a11713b27171" } } ], "extra": [ 1, 144, 64, 146, 60, 148, 214, 119, 207, 226, 4, 143, 148, 169, 44, 42, 10, 116, 48, 11, 142, 162, 62, 187, 15, 145, 75, 78, 43, 55, 119, 119, 38, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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