Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22a303b0dd5fef49f8549c7a266d7b0a782cf75460251aee049e60f46d69f18

Tx prefix hash: ec1670640f8784a89acfb9205b040bb52cf8653ad6fc059a6bc0dc38dc10fd2f
Tx public key: 8773113e173e4ed027f960287958ef5dadf78909f43437a570e3d9f2d4913b88
Timestamp: 1724762618 Timestamp [UCT]: 2024-08-27 12:43:38 Age [y:d:h:m:s]: 00:243:13:05:21
Block: 1097040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173939 RingCT/type: yes/0
Extra: 018773113e173e4ed027f960287958ef5dadf78909f43437a570e3d9f2d4913b88021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548a7e923a0ba11cf5dacf2efcdccf628e1ca25e8eb8ff2747cf7a02108beadd 0.600000000000 1572315 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": 1097050, "vin": [ { "gen": { "height": 1097040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548a7e923a0ba11cf5dacf2efcdccf628e1ca25e8eb8ff2747cf7a02108beadd" } } ], "extra": [ 1, 135, 115, 17, 62, 23, 62, 78, 208, 39, 249, 96, 40, 121, 88, 239, 93, 173, 247, 137, 9, 244, 52, 55, 165, 112, 227, 217, 242, 212, 145, 59, 136, 2, 17, 0, 0, 0, 1, 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