Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e40607ee721d25318c9dc6429f957dfa31ef11f5187b66e1fe5bd703f382d86

Tx prefix hash: 2e16dbedd24d1265f1532a9dd3b150931af4910dac89411724cb893a9677bfb4
Tx public key: d29d7e2490487ab6325b387fa623bbe82391b770615c1a868b1d596550441e99
Timestamp: 1632864347 Timestamp [UCT]: 2021-09-28 21:25:47 Age [y:d:h:m:s]: 03:095:11:48:42
Block: 342775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 844998 RingCT/type: yes/0
Extra: 01d29d7e2490487ab6325b387fa623bbe82391b770615c1a868b1d596550441e99021100000001fdc024ec000000000000000000

1 output(s) for total of 44.899816178000 dcy

stealth address amount amount idx
00: f44280ebf1c01776d7bec5a9a569b5d0274ea9e62285b2f2c6d96f0616f3cb8b 44.899816178000 703855 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": 342785, "vin": [ { "gen": { "height": 342775 } } ], "vout": [ { "amount": 44899816178, "target": { "key": "f44280ebf1c01776d7bec5a9a569b5d0274ea9e62285b2f2c6d96f0616f3cb8b" } } ], "extra": [ 1, 210, 157, 126, 36, 144, 72, 122, 182, 50, 91, 56, 127, 166, 35, 187, 232, 35, 145, 183, 112, 97, 92, 26, 134, 139, 29, 89, 101, 80, 68, 30, 153, 2, 17, 0, 0, 0, 1, 253, 192, 36, 236, 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