Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6a56247d39047fac877969e937e1ab2e3f86ee0b7ec1cb74f48a970201c9c2

Tx prefix hash: 6770d4832435d432473e0d9fba34b4ed428a4c0f3629a1983f3c5e84ef373a3e
Tx public key: e39c73220da7a4ce7db19a4ac349486197b3aaa1e64a5b8b81e3e46c921b265b
Timestamp: 1735960931 Timestamp [UCT]: 2025-01-04 03:22:11 Age [y:d:h:m:s]: 00:098:21:39:23
Block: 1189746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70470 RingCT/type: yes/0
Extra: 01e39c73220da7a4ce7db19a4ac349486197b3aaa1e64a5b8b81e3e46c921b265b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a49f604ff811231728d36fb61efdb10af7eb34de0d5950807b017c2ba53724ad 0.600000000000 1676257 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": 1189756, "vin": [ { "gen": { "height": 1189746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a49f604ff811231728d36fb61efdb10af7eb34de0d5950807b017c2ba53724ad" } } ], "extra": [ 1, 227, 156, 115, 34, 13, 167, 164, 206, 125, 177, 154, 74, 195, 73, 72, 97, 151, 179, 170, 161, 230, 74, 91, 139, 129, 227, 228, 108, 146, 27, 38, 91, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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