Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e341dcac7846a42f3129ca4ccb043f7ae48798857ff05926c0d1a70d57ac64bd

Tx prefix hash: fe79d8eaa327f16451563d2fafd902ebce23bf82619161e5080ab5fcac55feed
Tx public key: 281b446fe217444c478de34f10238ceddcc22b8594f5e5e1f034a13e3a0e21e4
Timestamp: 1728815370 Timestamp [UCT]: 2024-10-13 10:29:30 Age [y:d:h:m:s]: 01:054:10:06:11
Block: 1130643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297284 RingCT/type: yes/0
Extra: 01281b446fe217444c478de34f10238ceddcc22b8594f5e5e1f034a13e3a0e21e4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 850729f6e42d5b9f8bb2e57ef94df3ce221a583ded82bf817367c5895b9cbf1a 0.600000000000 1613520 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": 1130653, "vin": [ { "gen": { "height": 1130643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "850729f6e42d5b9f8bb2e57ef94df3ce221a583ded82bf817367c5895b9cbf1a" } } ], "extra": [ 1, 40, 27, 68, 111, 226, 23, 68, 76, 71, 141, 227, 79, 16, 35, 140, 237, 220, 194, 43, 133, 148, 245, 229, 225, 240, 52, 161, 62, 58, 14, 33, 228, 2, 17, 0, 0, 0, 3, 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