Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1fe570d0cb00d4d16294de66c28882ffc46814725fbb8dc6fc7e30cca35560

Tx prefix hash: 42e7d6c5b94820e37048d287146dd2d38c278c5aea375a6aed183b438d94e35b
Tx public key: 8c748fcdd852f22e429b5e92a693d85c117e6c1256694964d542b53872dc9768
Timestamp: 1703649822 Timestamp [UCT]: 2023-12-27 04:03:42 Age [y:d:h:m:s]: 01:064:08:51:20
Block: 922006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307082 RingCT/type: yes/0
Extra: 018c748fcdd852f22e429b5e92a693d85c117e6c1256694964d542b53872dc9768021100000006ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b04b10c0c227f09ec919b8cb530e410aad83a2549a0b5d4b11710255cfc8456 0.600000000000 1379700 of 15

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": 922016, "vin": [ { "gen": { "height": 922006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b04b10c0c227f09ec919b8cb530e410aad83a2549a0b5d4b11710255cfc8456" } } ], "extra": [ 1, 140, 116, 143, 205, 216, 82, 242, 46, 66, 155, 94, 146, 166, 147, 216, 92, 17, 126, 108, 18, 86, 105, 73, 100, 213, 66, 181, 56, 114, 220, 151, 104, 2, 17, 0, 0, 0, 6, 173, 86, 148, 172, 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