Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611702d658e83dec7a2277af1ce0813ee78029aace4213569afd0c244458e29f

Tx prefix hash: 23c59eda12c85d77f14555634661c76536dcb8da0925e3609dd09b02ec67a6c2
Tx public key: dd7d357ca6cb849dc6ea5e8add1a2634a230f2a1f4cde36b995ce07978d71a7e
Timestamp: 1729345368 Timestamp [UCT]: 2024-10-19 13:42:48 Age [y:d:h:m:s]: 00:157:14:37:32
Block: 1135028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112399 RingCT/type: yes/0
Extra: 01dd7d357ca6cb849dc6ea5e8add1a2634a230f2a1f4cde36b995ce07978d71a7e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb175a6733c2e554cb052363ce202c53227075d00aa715007570f41d8af7d8e 0.600000000000 1618357 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": 1135038, "vin": [ { "gen": { "height": 1135028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb175a6733c2e554cb052363ce202c53227075d00aa715007570f41d8af7d8e" } } ], "extra": [ 1, 221, 125, 53, 124, 166, 203, 132, 157, 198, 234, 94, 138, 221, 26, 38, 52, 162, 48, 242, 161, 244, 205, 227, 107, 153, 92, 224, 121, 120, 215, 26, 126, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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