Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fa161acd463f8bba3b4904f452f51ddd89cbb7a7b61626f0866214c95090e55

Tx prefix hash: 367555a3c60651b2d8edb5bf606dbf7dca6616340bd47de6fb878a3a89fd8661
Tx public key: 843a2398f16fe84b4752e35dc9a2df00d3f78aa8ea55db9c3471a0faea832cae
Timestamp: 1713201490 Timestamp [UCT]: 2024-04-15 17:18:10 Age [y:d:h:m:s]: 00:360:15:25:07
Block: 1001178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257843 RingCT/type: yes/0
Extra: 01843a2398f16fe84b4752e35dc9a2df00d3f78aa8ea55db9c3471a0faea832cae02110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c2b93570edb31c6a29cf38fa74547a90f2a60011234e067f7b6b054df3d582 0.600000000000 1461680 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": 1001188, "vin": [ { "gen": { "height": 1001178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c2b93570edb31c6a29cf38fa74547a90f2a60011234e067f7b6b054df3d582" } } ], "extra": [ 1, 132, 58, 35, 152, 241, 111, 232, 75, 71, 82, 227, 93, 201, 162, 223, 0, 211, 247, 138, 168, 234, 85, 219, 156, 52, 113, 160, 250, 234, 131, 44, 174, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 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