Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abd056caef774d8bc144d0593fb250d4e5f0572c2cf90b14b9a08188bb32e518

Tx prefix hash: 8b47a74415b13aeb8327e4a613195b62e9ce38a27e981df55dc441aa0d69df1d
Tx public key: a263eb2cc408af36cd2abd991a4600f8e42a7ff380eabf070daec9a640342d4e
Timestamp: 1694264128 Timestamp [UCT]: 2023-09-09 12:55:28 Age [y:d:h:m:s]: 01:067:06:06:49
Block: 844371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309358 RingCT/type: yes/0
Extra: 01a263eb2cc408af36cd2abd991a4600f8e42a7ff380eabf070daec9a640342d4e021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.977796384000 dcy

stealth address amount amount idx
00: 53e6ce4df9bdc5328a45f14307f686f7c9ca7def9abdcfd49ecf8692ceaa9763 0.977796384000 1297675 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": 844381, "vin": [ { "gen": { "height": 844371 } } ], "vout": [ { "amount": 977796384, "target": { "key": "53e6ce4df9bdc5328a45f14307f686f7c9ca7def9abdcfd49ecf8692ceaa9763" } } ], "extra": [ 1, 162, 99, 235, 44, 196, 8, 175, 54, 205, 42, 189, 153, 26, 70, 0, 248, 228, 42, 127, 243, 128, 234, 191, 7, 13, 174, 201, 166, 64, 52, 45, 78, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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