Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d6582ab4fa28062aca24c9eb1087f295acc1eb372df999bb2e6f5c39249b800

Tx prefix hash: 9a778eb6e366855c7f7e79a5918976548a0d72daf384cff7154c1e7276a0dae2
Tx public key: 5bf2679b43b62c812a52d6ca68993fee75e98f04a82bbad2fb648e9ea6af9f77
Timestamp: 1723710350 Timestamp [UCT]: 2024-08-15 08:25:50 Age [y:d:h:m:s]: 00:229:18:50:05
Block: 1088322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164084 RingCT/type: yes/0
Extra: 015bf2679b43b62c812a52d6ca68993fee75e98f04a82bbad2fb648e9ea6af9f77021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fab2add31c4bbcfe4b904fced1724670e00205365bccb8b9bc2ebd7c2a956e94 0.600000000000 1562937 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": 1088332, "vin": [ { "gen": { "height": 1088322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fab2add31c4bbcfe4b904fced1724670e00205365bccb8b9bc2ebd7c2a956e94" } } ], "extra": [ 1, 91, 242, 103, 155, 67, 182, 44, 129, 42, 82, 214, 202, 104, 153, 63, 238, 117, 233, 143, 4, 168, 43, 186, 210, 251, 100, 142, 158, 166, 175, 159, 119, 2, 17, 0, 0, 0, 4, 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