Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85430cd9057db0719731ecee4882a20a0c39f0b9234f7cc803b36dc71b456f5

Tx prefix hash: bb798798a8ccad0b1130a11828d69b4ab7536dc4435724d134052ad19b3571ce
Tx public key: 248e8fe49e1cdeedf33dcfef83b3ae8a8b5ccc10985cb8c0905433c88ed31a16
Timestamp: 1734874613 Timestamp [UCT]: 2024-12-22 13:36:53 Age [y:d:h:m:s]: 00:099:01:03:32
Block: 1180780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70544 RingCT/type: yes/0
Extra: 01248e8fe49e1cdeedf33dcfef83b3ae8a8b5ccc10985cb8c0905433c88ed31a160211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed6e7b710403cfd4db2e3f60987bb030a2392d71c82710b5ed34efb3db86b82d 0.600000000000 1667193 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": 1180790, "vin": [ { "gen": { "height": 1180780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed6e7b710403cfd4db2e3f60987bb030a2392d71c82710b5ed34efb3db86b82d" } } ], "extra": [ 1, 36, 142, 143, 228, 158, 28, 222, 237, 243, 61, 207, 239, 131, 179, 174, 138, 139, 92, 204, 16, 152, 92, 184, 192, 144, 84, 51, 200, 142, 211, 26, 22, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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