Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737c1ce560dfae1d4b77b1e9301d0fc48d9e6f51f0d8cfcfd8741a6518e6096d

Tx prefix hash: 24c42e455a1f1bb2b91970f407f873b1d6c5afa88065fe13a589d282e1865641
Tx public key: acb87147f6f105ed5a649cc6c03d9f8e614b867e879c5e54f8bccf0bcd1991f5
Timestamp: 1578231478 Timestamp [UCT]: 2020-01-05 13:37:58 Age [y:d:h:m:s]: 04:329:12:57:25
Block: 39213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124754 RingCT/type: yes/0
Extra: 01acb87147f6f105ed5a649cc6c03d9f8e614b867e879c5e54f8bccf0bcd1991f5021100000041dcee4b4d000000000000000000

1 output(s) for total of 455.063394106000 dcy

stealth address amount amount idx
00: 13e3a2ae3684b26e3cc6020b60fcb6827d6e62f0c758a58cc4103c64c533e019 455.063394106000 67453 of 0

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": 39223, "vin": [ { "gen": { "height": 39213 } } ], "vout": [ { "amount": 455063394106, "target": { "key": "13e3a2ae3684b26e3cc6020b60fcb6827d6e62f0c758a58cc4103c64c533e019" } } ], "extra": [ 1, 172, 184, 113, 71, 246, 241, 5, 237, 90, 100, 156, 198, 192, 61, 159, 142, 97, 75, 134, 126, 135, 156, 94, 84, 248, 188, 207, 11, 205, 25, 145, 245, 2, 17, 0, 0, 0, 65, 220, 238, 75, 77, 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