Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0722e989fc2a5fc8c9d52489f0d7f8fe9185669ba1a0bcc76397dff934e7efa8

Tx prefix hash: 779b239cbcdd61794cdf83c740241ade2e38b028780bd8c32a75fd58d1df7915
Tx public key: feb5516bf6e1d063b723bd62e7b77584b0075f1cb423359c20d69bbb50c60260
Timestamp: 1730868008 Timestamp [UCT]: 2024-11-06 04:40:08 Age [y:d:h:m:s]: 01:046:23:16:00
Block: 1147562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292047 RingCT/type: yes/0
Extra: 01feb5516bf6e1d063b723bd62e7b77584b0075f1cb423359c20d69bbb50c602600211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c2f685b5c14fea4117e39103b00fdd7e878701275e7b23fe95f21b04cc4bb0 0.600000000000 1632261 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": 1147572, "vin": [ { "gen": { "height": 1147562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c2f685b5c14fea4117e39103b00fdd7e878701275e7b23fe95f21b04cc4bb0" } } ], "extra": [ 1, 254, 181, 81, 107, 246, 225, 208, 99, 183, 35, 189, 98, 231, 183, 117, 132, 176, 7, 95, 28, 180, 35, 53, 156, 32, 214, 155, 187, 80, 198, 2, 96, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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