Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b79c5666f37a578f3502591ede707b80f1139bca188c5007a956b18ae04bc78

Tx prefix hash: 79b1006b7c13a06447a1db57a245f86fcabae7720b38012ea1bf0dcb522955a4
Tx public key: ddac36c95f94d501d4971d30ff87e4a6704e6f723eda997482e825c16d6da1f4
Timestamp: 1706426149 Timestamp [UCT]: 2024-01-28 07:15:49 Age [y:d:h:m:s]: 01:081:10:37:35
Block: 944995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319309 RingCT/type: yes/0
Extra: 01ddac36c95f94d501d4971d30ff87e4a6704e6f723eda997482e825c16d6da1f402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a40fb7f5c411b015ea42f09774ff77c6d16f62515b93e412b624144f626157be 0.600000000000 1403303 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": 945005, "vin": [ { "gen": { "height": 944995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a40fb7f5c411b015ea42f09774ff77c6d16f62515b93e412b624144f626157be" } } ], "extra": [ 1, 221, 172, 54, 201, 95, 148, 213, 1, 212, 151, 29, 48, 255, 135, 228, 166, 112, 78, 111, 114, 62, 218, 153, 116, 130, 232, 37, 193, 109, 109, 161, 244, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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