Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8787b0efae2d37fcbc887fc7b1a9decc7384c73b776673b9cf2b205c0e5627e5

Tx prefix hash: 0d560fd1dccf7313b48346eb64b9f8012b3a76963c455b9b5435935210ec3bb4
Tx public key: f90ed47c389fe73f300f2af2c06452660a8620899530fab8dc16c8ac27aa1cd3
Timestamp: 1701480456 Timestamp [UCT]: 2023-12-02 01:27:36 Age [y:d:h:m:s]: 01:057:02:50:46
Block: 904010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301977 RingCT/type: yes/0
Extra: 01f90ed47c389fe73f300f2af2c06452660a8620899530fab8dc16c8ac27aa1cd302110000000afaf35c9c000000000000000000

1 output(s) for total of 0.620353983000 dcy

stealth address amount amount idx
00: a640e7f3e016c9b22b814241ba7f5bbb0c0dd8496b783d67ed4e931e4d0bad0e 0.620353983000 1360713 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": 904020, "vin": [ { "gen": { "height": 904010 } } ], "vout": [ { "amount": 620353983, "target": { "key": "a640e7f3e016c9b22b814241ba7f5bbb0c0dd8496b783d67ed4e931e4d0bad0e" } } ], "extra": [ 1, 249, 14, 212, 124, 56, 159, 231, 63, 48, 15, 42, 242, 192, 100, 82, 102, 10, 134, 32, 137, 149, 48, 250, 184, 220, 22, 200, 172, 39, 170, 28, 211, 2, 17, 0, 0, 0, 10, 250, 243, 92, 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