Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03f3a9759c70137cca37ff2d0c3890f0731dbcfb7b7416a3e33fe7173de59cba

Tx prefix hash: ef0ad2455ac5a203e903eae4df8beeb67594cce0cb37f1b2c488e0caf9612f19
Tx public key: df9c85cfa0b3c047b202829f7eb52ea819c00aea5592c25c56cb673de6ba1767
Timestamp: 1725212917 Timestamp [UCT]: 2024-09-01 17:48:37 Age [y:d:h:m:s]: 00:265:23:22:42
Block: 1100780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189979 RingCT/type: yes/0
Extra: 01df9c85cfa0b3c047b202829f7eb52ea819c00aea5592c25c56cb673de6ba176702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 167d4bba6aa94e2a0163239946451a4913351e55be3b7f1176f96ed42a651880 0.600000000000 1576761 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": 1100790, "vin": [ { "gen": { "height": 1100780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167d4bba6aa94e2a0163239946451a4913351e55be3b7f1176f96ed42a651880" } } ], "extra": [ 1, 223, 156, 133, 207, 160, 179, 192, 71, 178, 2, 130, 159, 126, 181, 46, 168, 25, 192, 10, 234, 85, 146, 194, 92, 86, 203, 103, 61, 230, 186, 23, 103, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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