Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4611b90d0316e26a55bfd05a76055fec4521a38db603b9c67b8ada83d25a58c

Tx prefix hash: 9b8be82ef3d6a47b728a34320ddb1d4f22f1b8c18c44e8b86a2822965d771c2f
Tx public key: 38e491bdd10b2308bd84a0ca6170fb7de9f372f564649223112a29c65844a2cf
Timestamp: 1717838981 Timestamp [UCT]: 2024-06-08 09:29:41 Age [y:d:h:m:s]: 01:154:02:49:43
Block: 1039641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368716 RingCT/type: yes/0
Extra: 0138e491bdd10b2308bd84a0ca6170fb7de9f372f564649223112a29c65844a2cf021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851c44f10befd0e44679c9ad711a0f5bc4d7c7ebdc4c3c482d75028fa1f54ce8 0.600000000000 1508288 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": 1039651, "vin": [ { "gen": { "height": 1039641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851c44f10befd0e44679c9ad711a0f5bc4d7c7ebdc4c3c482d75028fa1f54ce8" } } ], "extra": [ 1, 56, 228, 145, 189, 209, 11, 35, 8, 189, 132, 160, 202, 97, 112, 251, 125, 233, 243, 114, 245, 100, 100, 146, 35, 17, 42, 41, 198, 88, 68, 162, 207, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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