Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fddf3fb6ecb2da4044353d9c8c2c41cf83e99178b1fc117c5990674a6c0f641

Tx prefix hash: 676dabe09d12204a70fa0b8fd6679fc2a514904ab58114d1a7855395ff33b51c
Tx public key: 1cc876b21a67c38bf1a655246aa964d3f865e72c1311a6f2c63cff971a6f90cf
Timestamp: 1620962522 Timestamp [UCT]: 2021-05-14 03:22:02 Age [y:d:h:m:s]: 03:301:18:51:31
Block: 260300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 976249 RingCT/type: yes/0
Extra: 011cc876b21a67c38bf1a655246aa964d3f865e72c1311a6f2c63cff971a6f90cf0211000000019c1fbdcc000000000000000000

1 output(s) for total of 84.240045303000 dcy

stealth address amount amount idx
00: 1db7b5d4ae79d37ce644f0f16c7c914f67911f3bcfeba541daf5b47ab60f2071 84.240045303000 548127 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": 260310, "vin": [ { "gen": { "height": 260300 } } ], "vout": [ { "amount": 84240045303, "target": { "key": "1db7b5d4ae79d37ce644f0f16c7c914f67911f3bcfeba541daf5b47ab60f2071" } } ], "extra": [ 1, 28, 200, 118, 178, 26, 103, 195, 139, 241, 166, 85, 36, 106, 169, 100, 211, 248, 101, 231, 44, 19, 17, 166, 242, 198, 60, 255, 151, 26, 111, 144, 207, 2, 17, 0, 0, 0, 1, 156, 31, 189, 204, 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