Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c060ea2e42489ad1ae0e07bfaf4d211f64b2439a1120fbcdbc6266ed11b1a5

Tx prefix hash: c7de039bd3cd20aeb5aab0e09a354823ece677b8a61547c0e6ea350dc949ba1c
Tx public key: 8255d12d7368dd64f77879ed253ac72426e7723bf7752f4ddab4cfe3e9dff8b8
Timestamp: 1631646166 Timestamp [UCT]: 2021-09-14 19:02:46 Age [y:d:h:m:s]: 03:173:22:11:50
Block: 333805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899725 RingCT/type: yes/0
Extra: 018255d12d7368dd64f77879ed253ac72426e7723bf7752f4ddab4cfe3e9dff8b80211000000018d0de867000000000000000000

1 output(s) for total of 48.080160297000 dcy

stealth address amount amount idx
00: f6b302eaf95c1538e95e6dda51939c548aa0f7501fc3837ca1a8bdce073ac02e 48.080160297000 688690 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": 333815, "vin": [ { "gen": { "height": 333805 } } ], "vout": [ { "amount": 48080160297, "target": { "key": "f6b302eaf95c1538e95e6dda51939c548aa0f7501fc3837ca1a8bdce073ac02e" } } ], "extra": [ 1, 130, 85, 209, 45, 115, 104, 221, 100, 247, 120, 121, 237, 37, 58, 199, 36, 38, 231, 114, 59, 247, 117, 47, 77, 218, 180, 207, 227, 233, 223, 248, 184, 2, 17, 0, 0, 0, 1, 141, 13, 232, 103, 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