Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbb11d99fb442d2a884b0b96de98e280318bce251a490739dd5cd68414f50687

Tx prefix hash: d461ea81cea3270e01ae65639dd50095bd1433a58e407473271ee2d43a4192bf
Tx public key: 88b93274708f312cf0099fedfa5deeb2efc609eba1c0e57df33b5b7d0d22f927
Timestamp: 1632142245 Timestamp [UCT]: 2021-09-20 12:50:45 Age [y:d:h:m:s]: 03:104:00:13:48
Block: 337544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850347 RingCT/type: yes/0
Extra: 0188b93274708f312cf0099fedfa5deeb2efc609eba1c0e57df33b5b7d0d22f92702110000007536fe6557000000000000000000

1 output(s) for total of 46.727983789000 dcy

stealth address amount amount idx
00: 3c7d70cb1d92efb92dc078e4eaa1adcaef7b6f8b74e958294c073529628e5b9c 46.727983789000 695015 of 0

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": 337554, "vin": [ { "gen": { "height": 337544 } } ], "vout": [ { "amount": 46727983789, "target": { "key": "3c7d70cb1d92efb92dc078e4eaa1adcaef7b6f8b74e958294c073529628e5b9c" } } ], "extra": [ 1, 136, 185, 50, 116, 112, 143, 49, 44, 240, 9, 159, 237, 250, 93, 238, 178, 239, 198, 9, 235, 161, 192, 229, 125, 243, 59, 91, 125, 13, 34, 249, 39, 2, 17, 0, 0, 0, 117, 54, 254, 101, 87, 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