Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff41ee204db97e2a28daa800730af00c95a770ec1b0364402288c1e7a922c57d

Tx prefix hash: 831e00925ce0b6046159a62f57e5b9fba8a29eea913b4a4b493a0ad6cef772da
Tx public key: 768c519b5959037604323ce56c969e3d7beeeecb61a1bec470904c9e5d86f4f4
Timestamp: 1585550571 Timestamp [UCT]: 2020-03-30 06:42:51 Age [y:d:h:m:s]: 04:291:20:04:22
Block: 89874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107725 RingCT/type: yes/0
Extra: 01768c519b5959037604323ce56c969e3d7beeeecb61a1bec470904c9e5d86f4f4021100000008a86a1a65000000000000000000

1 output(s) for total of 309.183292703000 dcy

stealth address amount amount idx
00: 02baaa4c5ca1e1f9f7e41cf97b87f72240c183a2e6e094fbbd20ef964f0d8f6f 309.183292703000 161060 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": 89884, "vin": [ { "gen": { "height": 89874 } } ], "vout": [ { "amount": 309183292703, "target": { "key": "02baaa4c5ca1e1f9f7e41cf97b87f72240c183a2e6e094fbbd20ef964f0d8f6f" } } ], "extra": [ 1, 118, 140, 81, 155, 89, 89, 3, 118, 4, 50, 60, 229, 108, 150, 158, 61, 123, 238, 238, 203, 97, 161, 190, 196, 112, 144, 76, 158, 93, 134, 244, 244, 2, 17, 0, 0, 0, 8, 168, 106, 26, 101, 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