Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be558f1927b40725f46aeca31bb4b1480261f50e39f3a2f194a4215f144880cb

Tx prefix hash: 496b0e21dcda377058f6a0a6fb7a2e29f136395ee93356de58d9d38ae961e52f
Tx public key: 368e2ff827fc523cc8e62d64d03bea285c1f919afd11e7edaea679d79f5862c1
Timestamp: 1578547949 Timestamp [UCT]: 2020-01-09 05:32:29 Age [y:d:h:m:s]: 05:055:15:14:01
Block: 41795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189687 RingCT/type: yes/0
Extra: 01368e2ff827fc523cc8e62d64d03bea285c1f919afd11e7edaea679d79f5862c10211000000c22264afe6000000000000000000

1 output(s) for total of 446.196400528000 dcy

stealth address amount amount idx
00: b3adb84ab97808d40989b3019de0a09ea8776f88f9bc0e0479fc036ebd0bb733 446.196400528000 74844 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": 41805, "vin": [ { "gen": { "height": 41795 } } ], "vout": [ { "amount": 446196400528, "target": { "key": "b3adb84ab97808d40989b3019de0a09ea8776f88f9bc0e0479fc036ebd0bb733" } } ], "extra": [ 1, 54, 142, 47, 248, 39, 252, 82, 60, 200, 230, 45, 100, 208, 59, 234, 40, 92, 31, 145, 154, 253, 17, 231, 237, 174, 166, 121, 215, 159, 88, 98, 193, 2, 17, 0, 0, 0, 194, 34, 100, 175, 230, 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