Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97c1fedf71e2b72ba6e2427b36b3a8ce23ac4323c038473a028ef1879ebb7eac

Tx prefix hash: 1c1646abe1d2add171ca85cac0cbcddcaa31f69a5ff603861b50c282a13f0de6
Tx public key: fcd1bd2e7af1d95dc32cb5dd126904f84f015b794b52e6261605452b9f006267
Timestamp: 1725365140 Timestamp [UCT]: 2024-09-03 12:05:40 Age [y:d:h:m:s]: 00:270:00:19:53
Block: 1102035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192878 RingCT/type: yes/0
Extra: 01fcd1bd2e7af1d95dc32cb5dd126904f84f015b794b52e6261605452b9f00626702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06a428f1d603242c09a8aab7883c0e0176f309b504a0a2d7d46bea6af97d2481 0.600000000000 1578314 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": 1102045, "vin": [ { "gen": { "height": 1102035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06a428f1d603242c09a8aab7883c0e0176f309b504a0a2d7d46bea6af97d2481" } } ], "extra": [ 1, 252, 209, 189, 46, 122, 241, 217, 93, 195, 44, 181, 221, 18, 105, 4, 248, 79, 1, 91, 121, 75, 82, 230, 38, 22, 5, 69, 43, 159, 0, 98, 103, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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