Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f7793e96065d60954b06e2ed2601ec24e8c3908c1c6a0f66efb89423d0d6988

Tx prefix hash: cc3c8347facd5dadf5f70d6882f475ee1539660cbe59a5e133bafa0a5fad7ef2
Tx public key: 58ff8c054f0f9bde26b5c455eb6ad3803d6cbbf98a5c6e329f425a77ae779d2b
Timestamp: 1733893287 Timestamp [UCT]: 2024-12-11 05:01:27 Age [y:d:h:m:s]: 00:112:19:10:22
Block: 1172650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80381 RingCT/type: yes/0
Extra: 0158ff8c054f0f9bde26b5c455eb6ad3803d6cbbf98a5c6e329f425a77ae779d2b021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb86adce26a62c464df298fb17fb091f34000324cb545f32cffc335deff450a 0.600000000000 1658569 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": 1172660, "vin": [ { "gen": { "height": 1172650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb86adce26a62c464df298fb17fb091f34000324cb545f32cffc335deff450a" } } ], "extra": [ 1, 88, 255, 140, 5, 79, 15, 155, 222, 38, 181, 196, 85, 235, 106, 211, 128, 61, 108, 187, 249, 138, 92, 110, 50, 159, 66, 90, 119, 174, 119, 157, 43, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 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