Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dabacb8fb875f02b8ddd33a92039efd68ab2a71e3753e1c18df38a5fde32fae9

Tx prefix hash: 4fc806a6935e280fc7482661f5d920600cdf614724e89861b1081b6aec4c34e7
Tx public key: 937fc51de1f6448be8157b89378b9006bdb11b2f388a20dfa1f3a4bfa850341a
Timestamp: 1713372737 Timestamp [UCT]: 2024-04-17 16:52:17 Age [y:d:h:m:s]: 01:056:18:41:25
Block: 1002610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301502 RingCT/type: yes/0
Extra: 01937fc51de1f6448be8157b89378b9006bdb11b2f388a20dfa1f3a4bfa850341a02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c407900683a52b35f255e2eea287eee50556b05aebf945f0c9e5b203e9c5a9b 0.600000000000 1463128 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": 1002620, "vin": [ { "gen": { "height": 1002610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c407900683a52b35f255e2eea287eee50556b05aebf945f0c9e5b203e9c5a9b" } } ], "extra": [ 1, 147, 127, 197, 29, 225, 246, 68, 139, 232, 21, 123, 137, 55, 139, 144, 6, 189, 177, 27, 47, 56, 138, 32, 223, 161, 243, 164, 191, 168, 80, 52, 26, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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