Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd709c2e1eb86582b456fea7cec60113d84c0d5483d5062d4fc6432957c10b7a

Tx prefix hash: 6731888fee9f26ca8fee6744cc8d4e66bd31843028196b91fee2ecf2ca6080f6
Tx public key: 4c220daa787e304d3d52d31c027e8f736ca7e5ef5a3b1e69d6f1ec3469749bda
Timestamp: 1605847081 Timestamp [UCT]: 2020-11-20 04:38:01 Age [y:d:h:m:s]: 04:070:01:16:55
Block: 149726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1057017 RingCT/type: yes/0
Extra: 014c220daa787e304d3d52d31c027e8f736ca7e5ef5a3b1e69d6f1ec3469749bda0211000001e8d3385d37000000000000000000

1 output(s) for total of 195.837701356000 dcy

stealth address amount amount idx
00: 3cbce532ed387213ea29f017c7525ae33c03a0437a2e17b2a774a24d98401176 195.837701356000 248766 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": 149736, "vin": [ { "gen": { "height": 149726 } } ], "vout": [ { "amount": 195837701356, "target": { "key": "3cbce532ed387213ea29f017c7525ae33c03a0437a2e17b2a774a24d98401176" } } ], "extra": [ 1, 76, 34, 13, 170, 120, 126, 48, 77, 61, 82, 211, 28, 2, 126, 143, 115, 108, 167, 229, 239, 90, 59, 30, 105, 214, 241, 236, 52, 105, 116, 155, 218, 2, 17, 0, 0, 1, 232, 211, 56, 93, 55, 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