Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 173a56ec59b3f37d3254b4ffd2a54b679d0701a8073c68b0253acfd81691e9e6

Tx prefix hash: 642e80d8b522b3a41a936e16075d26e96f199ceaa1f13406aa7ad94fb087e0e3
Tx public key: 6f8ae0f214641f8fb71c0e69ccb4debb2660106b424ee3b3fb9e8afb71e664c0
Timestamp: 1637607296 Timestamp [UCT]: 2021-11-22 18:54:56 Age [y:d:h:m:s]: 03:112:20:32:19
Block: 379868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859342 RingCT/type: yes/0
Extra: 016f8ae0f214641f8fb71c0e69ccb4debb2660106b424ee3b3fb9e8afb71e664c00211000000084a0f5013000000000000000000

1 output(s) for total of 33.834140851000 dcy

stealth address amount amount idx
00: 5634ecaf0de7eff54b8a03525844f6fd8448a9590ecef6800002bc0e4033329c 33.834140851000 767708 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": 379878, "vin": [ { "gen": { "height": 379868 } } ], "vout": [ { "amount": 33834140851, "target": { "key": "5634ecaf0de7eff54b8a03525844f6fd8448a9590ecef6800002bc0e4033329c" } } ], "extra": [ 1, 111, 138, 224, 242, 20, 100, 31, 143, 183, 28, 14, 105, 204, 180, 222, 187, 38, 96, 16, 107, 66, 78, 227, 179, 251, 158, 138, 251, 113, 230, 100, 192, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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