Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c315046548683a39615a84a22c70b4f7383d3b6caa2f3c71b7a56a436c416adc

Tx prefix hash: 2e19d3a448291787b2e152e131bf3f12557a76f0f1a29b1df8d28ea8fc02b4df
Tx public key: 9abcb574c3801ca6d0e9a7f5babd71fdd12f58da81b106b11ed08ee12c44fa4a
Timestamp: 1709189352 Timestamp [UCT]: 2024-02-29 06:49:12 Age [y:d:h:m:s]: 00:361:20:27:22
Block: 967941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258713 RingCT/type: yes/0
Extra: 019abcb574c3801ca6d0e9a7f5babd71fdd12f58da81b106b11ed08ee12c44fa4a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528c7f3d217f0ad0c23106fe2df1c08294756980e061a8d3bc3d1be0678479e8 0.600000000000 1427736 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": 967951, "vin": [ { "gen": { "height": 967941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528c7f3d217f0ad0c23106fe2df1c08294756980e061a8d3bc3d1be0678479e8" } } ], "extra": [ 1, 154, 188, 181, 116, 195, 128, 28, 166, 208, 233, 167, 245, 186, 189, 113, 253, 209, 47, 88, 218, 129, 177, 6, 177, 30, 208, 142, 225, 44, 68, 250, 74, 2, 17, 0, 0, 0, 1, 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