Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d65aec0d6e079b01186afe90257ad446e8c38e5c4cebd4d72b3b0030b313e978

Tx prefix hash: ea50f751450b5965b89044a9e725ed5028a62e35dddd8077a1eb1eda781768ef
Tx public key: b341e5f13b497f4f5a7aa4c84de749d9c4dd24e757be179d2842d3691dffca2e
Timestamp: 1718470314 Timestamp [UCT]: 2024-06-15 16:51:54 Age [y:d:h:m:s]: 00:279:21:57:57
Block: 1044882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200019 RingCT/type: yes/0
Extra: 01b341e5f13b497f4f5a7aa4c84de749d9c4dd24e757be179d2842d3691dffca2e0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e7541eda3d4ee0cd7201d252b5323f910ee27ebbaad32ee15c5526ed9823bf 0.600000000000 1514311 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": 1044892, "vin": [ { "gen": { "height": 1044882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e7541eda3d4ee0cd7201d252b5323f910ee27ebbaad32ee15c5526ed9823bf" } } ], "extra": [ 1, 179, 65, 229, 241, 59, 73, 127, 79, 90, 122, 164, 200, 77, 231, 73, 217, 196, 221, 36, 231, 87, 190, 23, 157, 40, 66, 211, 105, 29, 255, 202, 46, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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